Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change default sort orders of consensus callers #781

Merged
merged 3 commits into from
Feb 26, 2022

Conversation

nh13
Copy link
Member

@nh13 nh13 commented Feb 20, 2022

This affects CallDuplexConsensusReads and CallMolecularConsensusReads.

When no sort order is given, the output is unsorted but query-grouped,
which is sufficient for either downstream re-alignment or consensus
filtering. We can thus avoid sorting the output consensus reads when
calling.

I think picard MergeBamAlignment will not like this, as it wants queryname, not unsorted:querygrouped, so leaving this as a draft for now.

This affects CallDuplexConsensusReads and CallMolecularConsensusReads.

When no sort order is given, the output is unsorted but query-grouped,
which is sufficient for either downstream re-alignment or consensus
filtering.  We can thus avoid sorting the output consensus reads when
calling.
@nh13 nh13 requested a review from tfenne February 20, 2022 21:46
@codecov-commenter
Copy link

codecov-commenter commented Feb 20, 2022

Codecov Report

Merging #781 (c2a3c57) into master (f7b801e) will decrease coverage by 0.00%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #781      +/-   ##
==========================================
- Coverage   95.47%   95.47%   -0.01%     
==========================================
  Files         121      121              
  Lines        6852     6874      +22     
  Branches      461      464       +3     
==========================================
+ Hits         6542     6563      +21     
- Misses        310      311       +1     
Flag Coverage Δ
unittests 95.47% <ø> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
...fulcrumgenomics/umi/CallDuplexConsensusReads.scala 100.00% <ø> (ø)
...crumgenomics/umi/CallMolecularConsensusReads.scala 100.00% <ø> (ø)
...a/com/fulcrumgenomics/umi/UmiConsensusCaller.scala 93.23% <0.00%> (-0.76%) ⬇️
...fulcrumgenomics/umi/ConsensusCallingIterator.scala 100.00% <0.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f7b801e...c2a3c57. Read the comment docs.

@nh13 nh13 self-assigned this Feb 26, 2022
@nh13 nh13 marked this pull request as ready for review February 26, 2022 15:15
@tfenne tfenne merged commit adecf24 into master Feb 26, 2022
@tfenne tfenne deleted the feature/change-sort-order-of-consensus-callers branch February 26, 2022 15:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants